Content Delivery System, Delivery Server, Receiving Terminal, and Content Delivery Method

ABSTRACT

A transmitting terminal can transmit a content held by itself to a specific receiving terminal having no email software as if using a mailer. The transmitting terminal ( 10 ) and the receiving terminal ( 20 ) are connected to a delivery server ( 30 ) via a network ( 4 ). The delivery server ( 30 ) comprises: a database ( 36 ) for registering the device ID that specifies the receiving terminal ( 20 ); a content storage ( 39 ) for temporarily storing a content transmitted from the transmitting terminal ( 10 ); and table ( 33, 37 ) for managing contents separately on a per device ID basis of the receiving terminal. The delivery server ( 30 ), when receiving a request from the receiving terminal ( 20 ), refers to the tables ( 33, 27 ) and transmits to the receiving terminal ( 20 ) a content, the transmission destination of which corresponds to the device ID of the receiving terminal ( 20 ).

This application is a continuation application of U.S. patentapplication Ser. No. 15/465,964, filed Mar. 22, 2017, which is acontinuation application of U.S. patent application Ser. No. 15/055,629,filed Feb. 28, 2016, now U.S. Pat. No. 9,661,101, which is acontinuation application of U.S. patent application Ser. No. 13/914,632,filed on Jun. 11, 2013, now U.S. Pat. No. 9,313,295, which is acontinuation application of U.S. patent application Ser. No. 12/746,881,filed on Jun. 8, 2010, now U.S. Pat. No. 8,484,299, which is the USnational phase of International Application No. PCT/JP2009/000292 filedon Jan. 27, 2009, which claims the benefit of priority to JapanesePatent Application No. 2008-048389, filed Feb. 28, 2008 and JapanesePatent Application No. 2008-136185, filed May 26, 2008, the content ofwhich are hereby incorporated by reference in its entirety for allpurposes.

TECHNICAL FIELD

This disclosure relates to a content delivery system for deliveringcontent such as pictures to a particular receiving terminal via anetwork, a delivery server used in this system, and a technique forauthenticating a user device when receiving content from the deliveryserver.

BACKGROUND ART

Electronic mail (hereinafter e-mail) is generally used to transmitinformation to only a particular person. In this case, of course, both atransmitting device and a receiving device need to have e-mail software.Lately, most of PC (personal computer) purchasers make use of e-mail, soe-mail software is usually installed in a PC sold.

Meanwhile, TV products capable of connecting to a network have latelygone on sale. However, TVs may not be connected to networks as often asPCs. E-mailing with a TV set that a family often view together would beutilized less frequent than PCs. Thus, installing e-mail software in aTV set is impractical in terms of development cost in spite of havingthe capability of connecting to network.

It is possible that a TV set connected to a network accesses a serverand requests a content delivery from the server, even though having noe-mail software. Patent Document 1 discloses a method for scheduling adownload. This document states that this method measures the rate ofdownloading a test file, predicts time utile completion, sets a date andtime to start a download so as to complete it at a user-desired time,and schedules the download, gaining agreement with the user. If the userdoes not agree, an alternative data and time to start a download ispresented. Another method is also described in which download status ismonitored and switching to another server takes place if the download isnot likely to complete until a guaranteed end time. In Patent Document2, a method is described in which a time zone in which a download isscheduled is divided and assigned to terminals, thus distributing loads.

Further, services like above-mentioned e-mail on TV are expected toincrease in future. To accommodate this, a method for authenticationsignaling between a service receiving device and a service deliveryserver is described in Patent Document 3.

-   Patent Document 1: Japanese Laid-Open Patent Application No.    2003-67280-   Patent Document 2: Japanese Laid-Open Patent Application No.    2004-185114-   Patent Document 3: Japanese Laid-Open Patent Application No.    2001-350724

DISCLOSURE OF INVENTION Problems to be Solved by the Invention

According to the above-mentioned patent documents 1 and 2, it ispossible that a terminal (TV set) having no e-mail software accesses adelivery server and downloads desired content at a desired date/time.However, both of these prior arts assume the situation access is madefrom a terminal (TV set) to the server, but do not consider a scenarioin which the terminal receives content that belongs to a particularperson or a sender transmits content that the sender owns to aparticular terminal (TV set). Thus, a technique is required to allowtransmission of content owned by a sender to a particular terminal (TVset) without e-mail software installed therein.

According to the above-mentioned patent document 3, authentication isperformed using a device specific ID and authentication can be performedwhen the above-mentioned service is provided. However, no considerationis taken for more secure authentication that is effected even for avariety of services assumed to be added. Thus, a more user-friendlyauthentication technique is called for.

An object of the present invention is to make it possible to adapt tothe addition of a diversity of service including, inter alia, a servicein which a transmitting terminal can transmit content that belongs toits user (owner) to a certain receiving terminal having no e-mailsoftware in an easy-to-use manner like via e-mail and to provide theseservices protected by secure authentication that is accomplished withoutbothering users.

Means for Solving the Problems

There is provided a content delivery system comprising a transmittingterminal, a receiving terminal, and a delivery server which areconnected via a network and configured to transmit content from thetransmitting terminal to the receiving terminal via the delivery server,the delivery server comprising a database for registering device IDs,each identifying each receiving terminal, a content storage fortemporarily storing contents transmitted from transmitting terminals,and a table for sorting and managing contents by receiver terminal'sdevice ID and by sender. In response to a request from a receivingterminal, the delivery server refers to the table and transmits contentdestined to the receiving terminal's device ID to the receivingterminal.

Advantageous Effects of the Invention

A sender can transmit content to a receiving terminal without e-mailsoftware in an easy-to-use manner like via e-mail. Because a receivercan receive content after verifying the sender, the receiver does nothave to receive transmissions of unwanted contents from the generalpublic.

The above-discussed service and the like can be made use of securely anda service server typified by a delivery server is independent of anauthentication server. It is thus possible to implement anauthentication server that endures the addition of a diversity ofservices.

BEST MODE FOR CARRYING OUT THE INVENTION

In the following description of embodiments, a transmitting terminal isassumed to be a PC or a mobile phone and a receiving terminal a TV set.Content covers motion pictures captured by, for example, a video camera,and still pictures captured by a digital camera. These motion and stillpictures are together referred to as pictures. Since a TV set has noe-mail address, an individual TV has a device ID identifying it, storedon its internal memory during its manufacturing process, and the usercan know the device ID by retrieving it from the memory via a remotecontroller or the like of the TV set. A sender transmits picturesattached with the device ID of the originating TV set as a key. Tocontrol transmission and reception of pictures, a server is installed ina center and connected to a network. Every PC registers with the serveras a member that is a sender. At this time, the sender also registers onthe server the device ID of a TV set of the other party to which thesender wants to transmit pictures.

When a TV set accesses the server via the network, a confirming messageas to whether to accept a registered sender is displayed on the screenof the TV set. If the receiver accepts the sender, the sender'registration becomes valid and the server initiates a service ofpreserving pictures received from the sender. After preserving pictures,the server sends a picture arrival message that is displayed on theregistered receiver's TV screen. When the receiver selects a desiredpicture, the receiver can receive and view it from the server.

First Embodiment

FIG. 1 illustrates an example of overall architecture of a contentdelivery system according to a first embodiment. This system isconfigured such that a transmitting terminal (PC 10), a receivingterminal (TV set 20), and a delivery server (server 30) which relays acontent delivery between both terminals are connected to a network 4such as Internet. In this system, from the PC 10 having e-mail software,picture content belonging to the sender is transmitted to a TV set 20having no e-mail software via the server 30.

The sender residing in the sender's home 1 copies picture content(hereinafter, also referred to as a picture file or video) captured by avideo camera 11 or digital camera 12 to the PC 10. The PC 10 connects tothe network 4 via routers (not shown) and transfers the picture to andhas it preserved on the server 30 situated in the center 3. The server30 preserves the picture transferred from the sender (PC 10) and waitsfor access from the TV set 20 in the receiver's home 2 of a receiverspecified by the sender. When the TV set 20 has connected to the server30 situated in the center 3 via the routers and the network 4, theserver 30 sends the TV set 20 a message indicating the arrival of thepicture and the message is displayed on the screen of the TV set 20.After that, the receiver can select, receive, and view the picture. Ifthe TV set 20 has a self-contained storage (e.g., a hard disk), thepicture can also be downloaded.

The server 30 needs to have a function of identifying the TV set 20which is the receiving terminal. It is therefore efficient that thecenter 3 carrying out such a content delivery service using the server30 is set up and operated by the same entity as the manufacture of theTV set 20. To identify the TV set 20 which is the receiving terminal,the device ID of each TV set 20 is used as an address. Besides picturetransmission from the PC 10 in the sender's home, the sender cantransmit a picture file captured by a mobile phone 50 which has beenregistered beforehand with the server from the mobile phone 50 to theserver 30 via the network 4, which will be described in a secondembodiment. Hereinafter, the content delivery service carried out by thecenter 3 (server 30) will be referred to as a “video delivery service”.

Next, the server 30 and the TV set 20 are described in detail regardingtheir internal structures.

FIG. 2 is a diagram showing an exemplary internal structure of theserver 30.

A network transceiver 31 is connected to an external network 4 andperforms communication with a PC 10 and a TV set 20 via the network.

A member information manager 32 has data bases and tables, i.e., anunread e-mail check table 33, a sender DB 34, a receiver DB 35, a TVdevice DB 36, and a content management table 37 to store information forsenders and receivers and preserved contents information. When theserver is accessed from a PC 10 or TV set 20, the member informationmanager 32 performs processing for member information verification,registration, or others, referring to a related database or table.

For example, if the server receives data for a tentative memberregistration from the PC 10 of a sender, the manager 32 registersinformation for device ID, user ID, etc. into the unread e-mail checktable 33. If the server receives a response as to whether the receiveraccepts the sender from the TV set 20, the manager 32 updates thecontents of the sender DB 34 and the receiver DB 35 according to theresponse. If the server is accessed from a TV set 20, the manager 32requests the TV set 20 to send its device ID and acquires it. Themanager 32 compares the acquired device ID with information stored inthe TV device DB 36 and verifies whether the device ID is valid. In casethe device ID is invalid, the manager 32 detects the invalidity at thispoint of time and rejects subsequent processing for the TV set. Thecontent management table 37 is used to manage preserved contentstransferred from users and hold service agreements made with each user.

A content transceiver 38 receives picture content from the PC 10 andtransmits picture content to the TV set 20. A content storage 39 storespicture contents received and to be transmitted. Specifically, thecontent transceiver 38 stores picture content uploaded from the PC 10into the content storage 39 and, in response to a request from the TVset 20 for a picture to receive and view or a request to download apicture, reads the picture content from the content storage 39 andtransmits it to the TV set 20.

FIG. 3 is a diagram showing an exemplary internal structure of the TVset 20.

A network transceiver 21 is connected to an external network 4 andperforms communication with the server 30 via the network. A browser 22renders screen information such as an e-mail screen and an acceptancescreen and outputs it to a display 27 according to information describedin a form of HTML, BML, etc. transmitted from the server 30. A picturereproducer 23 decodes a still or motion picture file contained inpicture content transmitted from the server 30, reproduces the still ormotion picture, and outputs it to the display 27.

A device ID sender 24 reads device ID information assigned to the TV set20 from a device ID storage 25 and sends it to the server 30 in responseto a request from the server 30. In the device ID storage 25, the deviceID information specific to the TV set 20 is stored and retained. Thisdevice ID information is assigned to each terminal and written into thedevice ID storage 25 during the manufacturing of the TV set 20. When theuser wants to know the device ID, the user can retrieve it and displayon the display 27, e.g., by operating an attached remote controller.

A content storage 26 is, for example, a hard disk storage device andpicture content received from the server 30 is downloaded and storedinto it. The user can read a picture stored and view it via the picturereproducer 23 at any time the user wants to do.

The storage 26 may be either self-contained or external. The display 27displays pictures and/or information output from the browser 22, picturereproducer 23, and device ID sender 24 on the screen.

FIG. 4 is a flowchart illustrating a process flow of the contentdelivery service (video delivery service) of the first embodiment.First, the process is outlined in order of steps.

Step S101: A sender acquires the device ID of a receiving terminal (TVset 20) of the other party and the URL of the server 30 to which the TVset 20 is connected. Reversely, the receiver may tell the sender ofpictures the device ID of the TV set 20 and the URL of the server 39 bytelephone or fax. For this purpose, the device ID to identify the TVdevice is stored in the device ID storage 25 of the TV set 20. Thisdevice ID is used as an address for picture transmission. The device IDis readily retrievable so that the TV owner can easily know the deviceID like a B-CAS card number using the remote controller or the like.

Step S102: The sender accesses the server 30 from the PC 10 and inputsinformation for the sender and receiver according to the aboveinformation (the device ID of the TV set 20 and the URL of the server30). This is referred to as a tentative member registration. Inparticular, as sender information, the e-mail address of the sender asuser ID, sender's address, name, name for display, birth date, telephonenumber, etc. are registered. As receiver information, the device ID ofthe TV set 20 and the receiver's name for display are registered. Theseitems of information are tentatively registered on the database of theserver 30.

Step S103: The server 30 in the center 3 notifies the receiver's TV set20 that the tentative member registration has been made, using thedevice ID. In response to this, the receiver verifies and accepts thecontents of the tentative registration. To do this, because the TV set20 has no e-mail software installed, notification is accomplished asfollows. In the unread e-mail check table 33 on the server 30, deviceIDs for which tentative registration has been made are flagged. Whenaccessed from a TV set 20, the server 30 refers to this table and checkswhether the device ID of the accessing TV set is flagged. If the deviceID is flagged, the server retrieves the user ID and name of the senderfrom the sender database 34 and sends the TV set 20 a message “Personnamed OO is trying to send a picture file to you” to be displayed on theTV set 20. The receiver accepts the sending if the displayed sender(person named OO) is a favorable one.

Step S104: When the receiver accepts the sender displayed on the TV set20, the server 30 changes the tentatively registered member informationto a definite registration. It also notifies the sender by e-mail abouta result as to whether the receiver has accepted the sender. The servermay use the e-mail address previously registered at the tentative memberregistration. Upon the definite registration, the server 30 initiatesthe service of preserving pictures transferred from the registeredsender. In other words, it is impossible for the sender to transferpictures to and have them preserved on the server 30 until the receiverhas accepted the sender. Thus, the server 30 can avoid doing anunnecessary preservation service.

Step S105: By operating the PC 10, the sender specifies the receiver whoaccepted the sending and transmits (uploads) a picture captured by thevideo camera 11 or digital camera 12. The server 30 stores the picturetransmitted from the PC 10 into the content storage 39. Then, the server30 preserves the picture until receiving a request from the specifiedreceiver to receive it.

Step S106: The server 30 converts the format (file format) of thepicture preserved into a format enabling the picture to be displayed onthe TV set 20, as necessary. For example, in the case of motionpictures, a file format thereof stored on the PC 10 may not bereproduced as is on the TV set 20, though can be reproduced on PC. Bypicture format conversion performed in the server 30, the load on the TVset 20 can be alleviated.

Step S107: When a receiver accesses the server 30 from its TV set 20,the server 30 looks through the unread e-mail check table 33. If anunread e-mail flag is set for the device ID of the accessing TV set 20,it means that the receiver has not yet received the e-mail (picturecontent). In that case, the server 30 notifies the TV set 20 thatpictures addressed to it arrived at the server. The receiver selects adesired picture, receives it from the server 30, and views it on the TVset 20.

Step S108: If the TV set 10 has a self-contained storage 26 such as ahard disk, it is possible to store (download) the received picture. Itis also possible to erase some (if unwanted) of previously storedpictures by operating the TV set 20. With regard to erasing pictures,the sender is also able to erase the picture as preserved on the server30 by operating the PC 10. That is, at least either of the sender andthe receiver has a right to erase pictures for transmission andreception.

Step S109: If the sender has more pictures to be transmitted, the sendertransmits a next picture to the server 30, returning to step S105. Thatis, member registration in steps S101 to S104 is completed only once atthe first time. These steps are skipped at a second time and subsequentand picture transmission can take place anytime between the registeredsender and receiver.

The content delivery service implemented by this system provides thefollowing advantages:

(a) It is difficult to install additional software like e-mail softwarein TV sets, a home appliance product, that serve as a receivingterminal. Reasons for this are: the cost for developing such softwareand testing its operation is high; and upgrade is hard to do includingverifying compatibility with former products. In this respect, thissystem enables transmission and reception of picture content withoutinstalling e-mail software in the TV set.(b) A wide range of users including elders may have a lot of chances ofoperating TV sets, a home appliance product, unlike PCs. Input means forusing a remote controller are also limited. It is therefore requiredthat anyone can operate TV sets easily and readily and without erroneousoperation for using the present system and service. In this regard, thepresent system dispenses with the input of a personal ID to identify hisor her own account, instead, by using a unique device ID assigned toeach device for identifying a TV set, which allows for preventingerroneous operation.(c) After the receiver verifies and accepts the sender, the server isconfigured to preserve contents transferred from the sender and transmitthe contents to the receiver. Accordingly, the receiver does not have toreceive transmissions of unwanted contents like spam e-mails from thegeneral public. Moreover, the delivery service can avoid unnecessarypreservation of contents

In the following, each of the steps of the content deliver service inFIG. 4 will be explained in greater detail.

(1) Telling the Sender the Receiver's Device ID and Server's URL (StepS101)

The vendor providing the “video delivery service”, which may be, forexample, a TV manufacturer, should state the address (URL) of the server30 that carries out this service in a home page to be viewed in thecooperate website, a brochure of the TV set, a leaflet enclosed with theTV set, etc. This device ID is used as an address for picturetransmission. The device ID of the TV set is stored in the device IDstorage 25 and is readily retrievable so that the user can easily knowthe device ID like a B-CAS card number by operating the remotecontroller.

This device ID is used like an e-mail address. Preferably, someelaborate protection is taken to avoid transmission of the device ID toa third party, even if the sender inputs it incorrectly. For thispurpose, it is preferable to present a converted device ID processed toprevent an incorrect input to the user, instead of presenting the deviceID itself. For example, if an original device ID is 32 bits long, it isdivided into four parts of 8 bits and a check sum is calculated byadding the bits of the respective four parts. Last 8 bits of the checksum is taken and linked to the original device ID to generate aconverted device ID having a total of 40 bits. This converted device IDis presented to the user.

The converted device ID thus generated has a very low possibility ofmatching with the converted device ID of a third party including eventhe check sum, even if the sender has input a partially incorrect ID.Also, when the server are collating the check sums, there is a highpossibility of a mismatch being found. Thus, there is little possibilityof erroneous transmission of a device ID to the TV set of the third partand safety can be enhanced.

In a case that the above conversion processing is implemented, in the TVset 20, the conversion processing can be performed when the device IDsender 24 in FIG. 3 has read the device ID, as previously described. Atthe server 30 side, after acquiring the device ID from the TV set 20,the member information manager 32 in FIG. 2 performs a reverseconversion of the ID to its conversion performed in the TV set 20.Thereby, it is possible to restore the converted ID to the device IDbefore being converted, held in the device ID storage 25 of the TV set20.

In the following description, especially, in first, second, and thirdembodiments, the device ID refers to either the original device ID orthe above converted device ID.

The TV set owner tells the other party (his or her family, friends,relatives, etc.) from whom he or she wants a video transmission thedevice ID of his or her TV set and the URL of the portal (server) of theservice provider by telephone or fax and requests the other party tomake a member registration for the “video delivery service”.

(2) Tentative Member Registration (Step S102)

The sender executes a member registration (tentative) for the “videodelivery service”, using the device ID and the server's URL acquiredfrom the receiver. The PC 10 of the sender is equipped with the browser22 and the following operations are performed by the browser. From thePC 10, the sender accesses the above URL and proceeds with the memberregistration. FIGS. 9 through 14 show display screens for memberregistration.

FIG. 9 is a top screen of the video delivery service. If the sender doesnot yet have a user ID, the sender performs a user registration bypressing the “User registration” button. FIG. 10 is a screen to displaythe terms and personal information handling conditions. FIG. 11 is ascreen to enter the device ID of a TV set of destination. In thisdisplay screen, a term “destination ID” which is easy to understand forthe user is used instead of device ID. In the following, “destinationID” has the same meaning as “device ID”. FIG. 12 is a screen to enterinformation for the receiver and the sender. FIG. 13 is a screen toconfirm the entry.

FIG. 14 is a screen to indicate the tentative registration completed.

Upon the completion of the tentative registration, the server 30registers the tentative registration contents into the unread e-mailcheck table 33. FIG. 5 shows an example of the unread e-mail check table33. In the table, for each device ID, flags are provided to indicatewhether there is a person waiting to be accepted as a sender and whethera new picture file has been transferred from an accepted sender. In thisexample, for the TV set with the device ID of “1234567”, there are twosenders requesting to be accepted and their user IDs (ID 1, ID 2) arespecified. This example also indicates that an e-mail (actually,pictures) from an accepted user (ID 1) has arrived and the receiver ofthis TV set does not yet read the e-mail.

(3) Acceptance by the Receiver and Definite Member Registration (StepsS103, S104)

FIG. 15 shows an initial screen for the receiver to access from the TVset 20 to the server 30 in the center 3. This screen corresponds to theinitial screen for the PC 10 upon connecting to the Internet. Theaccess-destination address is stored in the TV set 20. In this screen,the video delivery service is shown as “Video delivery”. The server 30refers to the unread e-mail check table 33 in FIG. 5 and displays thestatus of a person waiting to be accepted as a sender and the status ofa picture file transferred from an accepted sender on a screen thatfollows.

In a case where a sender who completed a tentative registration waits tobe accepted by the receiver, the receiver may choose “video deliveryservice” on the screen of FIG. 15. The receiver may choose “videodelivery service” by moving the cursor vertically and horizontally to itand pressing the Fix key or using a numeric keypad of the remotecontroller in which key numbers are associated with the services.

FIG. 16 is a screen to accept a sender. In this example, a text meansthat “as a person Taro completed a tentative registration, he wants youto accept him”. The receiver decides whether or not to accept the senderand may choose “O=acceptance” or “X=rejection”, using the remotecontroller of the TV set. If the receiver chooses “A=I don't decideabout it”, the receiver also may decide later whether or not to acceptthe sender (FIG. 32).

In a case where an accepted user has transferred a new picture file tothe server, the screen shows “newly arriving e-mail: 1” as in FIG. 15 toindicate that there is a newly arriving picture. Then, the screenprompts the receiver to choose “video delivery” and open a receivede-mail list. The term “e-mail” is used in the display screen. Becausethe TV set 20 does not have e-mail software installed, it does notreceive e-mail technically. The wording “e-mail” is used, taking accountof the easiness to understand for the user (sender, receiver).

When the receiver accepts the sender, the sender executes a definiteregistration from the tentative member registration and the server 30adds the definite registration contents to the sender DB 34 and thereceiver DB 35.

FIG. 6 shows an example of the sender DB. The tentative registrationcontents are inserted in the columns from “user ID” to “birth date” andthe device ID (already entered at the tentative registration) of the TVset of the receiver who accepted to receive (permitted transmission)with the count of receivers=1 is registered upon the definiteregistration. Credit card number, expiry date, and join data entered bythe user at the definite registration are additionally registered. Sincetransmission from a mobile phone is possible, columns for mobile phonesare provided and these columns are filled when a mobile phone is added.The count of receivers=3 in FIG. 6 is due to that two receivers areadded after the definite registration.

FIG. 7 shows an example of the receiver DB and receiver data isadditionally registered upon the definite registration. Initially, thecount of senders=1 is set and the user ID (user ID 5 in this case) ofthe sender permitted to transmit to the receiver is registered.Subsequently, the user count increments each time another sender ispermitted to transmit to the receiver and its user ID (user ID 6 in thiscase) is added. As information identifying a person in the receiver DB,only the device ID and the name for display are possible to implementthe service. However, taking account of possibility of later change toreceiver charging, management for such change is facilitated by entry ofaddress, name, telephone number, and birth date as well. At theregistration screen of FIG. 12, these items of information may beentered by the user. FIG. 7 shows the contents of the database withthese items of information added. Once sender data and receiver data areadditionally registered in the sender DB and the receiver DB, the sendercan transmit e-mail to the receiver.

When the receiver accepts the sender, the server transmits e-mailincluding a message “you has been accepted” to the sender and notifiesthe sender of URL of the site at which a definite registration can beexecuted. The sender enters this URL on the PC 10 and accesses a screenfor definite registration. FIG. 17 shows an example of the screen fordefinite registration. The sender sets a password and a query and answerin case the sender forgot the password. Three courses, i.e., flat-ratebasic, flat-rate high grade, and metered rate courses are set and thesender may choose one of them. In the flat-rate course, a fixed capacityof a hard disk can be used and a flat-rate charge is imposed. In thehigh grade course, the available capacity of a hard disk is larger.Meanwhile, in the metered-rate course, a fixed charge is imposed for onetime of use of service up to a given capacity and the server 30automatically removes the content after a predetermined period elapsed.Because sender charging is assumed in the first embodiment, the senderis requested to enter credit card number, expiry date, and security codeon this registration screen. It is possible that the sender may beprompted to enter credit card information when executing a tentativemember registration in the previous section (2). However, after cardauthentication is completed, the start of charging must be prevented,unless the sender is accepted by the receiver. In the first embodiment,the sender is prompted to enter credit card information at a definiteregistration after which charging can begin.

(4) Uploading Picture Files from PC (Step S105)

Upon the login done on the screen of FIG. 9 from the PC 10, a screen tocreate an e-mail as in FIG. 18 is displayed. Here, the sender may choose“Create e-mail” and select a receiver and an attached file. The names ofaccepted receivers are displayed in a “destination” (mandatory)” box inthe middle of the screen. The sender may select a receiver(s) from amongthem. When choosing a check box, the check mark is displayed.

FIG. 19 shows the contents of an e-mail created. When pressing an “Add afile” button 201 in an upper section of the screen, a screen 202 toselect a file from the files stored in the PC 10 is pop-up displayed.For graphical convenience, the file selecting screen 202 is shown in alower section of the screen. From among these files, the sender mayselect a file that the sender wants to transmit. For the selected file,its file name with a thumbnail, together with the date of creation, isdisplayed in a file list 203 in the screen on the PC 10. In FIG. 19, anexample where three attached files have been selected is shown. In thedestination list 204, two receivers are selected as destinations fromthe list. In the list 204, a receiver attached with a “reception stop”mark denotes that the receiver sets the receiving mode to rejectreception from the sender now by the user's intent, although onceaccepted the sender in the past.

Joining picture files transmitted into a single file is explained below.When video recording is performed with the video camera 11, a singlemotion picture file may be created for one scene from the recordingstart to a stop. In that case, when the picture file is copied from thevideo camera 11 to the PC 10, it is often divided into a plurality offiles and information for one event such as a school athletic meet and aschool play is composed of a plurality of files. In most cases, filesassociated with an event may be handled together. Thus, in such cases,the sender usually need to upload a plurality of files in one e-mail.

On the other hand, from the receiver's standpoint, when receiving onee-mail including a plurality of files like the above ones correspondingto the parts of a whole, it is convenient that a whole of the files canbe reproduced in order by a single reproducing operation, rather thanreproducing each of the files one by one by repeating the reproducingoperation. Taking account of this point, in the first embodiment, in acase where the sender uploads a plurality of files at a time, the server30 is configured to join these files. In the first embodiment, theserver 30 joins the files in order in which the sender attached thefiles on the screen of FIG. 19 into a single file. Even after listingfiles in the file list 203 in FIG. 19, the list allows for reordering sothat the files can be reordered by selecting a file. When the receiverreproduces the files, a set of the files joined in order as above willbe reproduced.

In the first embodiment, picture files include motion pictures and stillpictures. Because these pictures may be mixed and uploaded, the serverhandles the files as follows:

(a) If only motion picture files are transmitted at a time, the server30 joins them in order in which they were attached into a single motionpicture file.(b) If only still picture files are transmitted at a time, the serverhandles them as separate files and does not join them. The files aredisplayed on the TV set one by one separately like icons.(c) If motion and still picture files are mixed and transmitted at atime, the server joins the motion picture files in order in which theywere attached into a single motion picture file until finding a stillpicture file. The server handles still picture files one by one, so thatthey are displayed in order in which the sender attached them. At thereceiver side, One motion picture file is reproduced and still picturesare displayed such that one is displayed for several second and thenanother is displayed similarly (still pictures are displayed, while amotion picture is reproduced).

In the foregoing (a) to (c), motion pictures are joined into a singlefile, wherever possible, as described above. Needless to say, however,motion picture files may remain separate as is without being joined intoa single file and they may be reproduced one by one in order in whichthey were attached.

A restriction can be imposed not to permit mixing of motion and stillpictures in one e-mail. In that case, the sender is prompted to selecteither motion or still picture to be transmitted in an e-mail. Bychecking file extensions, if a file of a wrong type is attached, awarning message such as “the file is not motion picture (still picture)”is issued to the sender, so that attaching such a file is not accepted.In FIG. 19, an example of an error message 205 “this is other thanmotion/still picture files” is shown. In a case where both motion andstill pictures are handled, if a file other than those is attached, thesender is alerted as in the above example. In a case where only motion(still) pictures are handled, if a file other than the specified type isattached, the sender is alerted by the appropriate error message.

When the sender wants to transmit video to a new receiver, by choosing“Add/Edit destinations” in FIG. 18, a screen to add and editdestinations as in FIG. 20 is displayed. The sender enters informationfor a new receiver and waits until it is accepted by the receiver. In acase where personal information such as address and name should beinput, an item may be set to switch from the screen of FIG. 20 to thescreen of FIG. 12 and enter such information.

(5) Picture Format Conversion (Step S106)

As for motion pictures, a file format of pictures stored in the PC 10may not be always reproduced as is on the TV set 20, even if the filecan be reproduced on the PC. The server 30 executes a picture formatconversion to convert it into a file format that can be displayed on theTV set.

A motion picture file is generally constructed as follows. Primarily,there are a video elementary stream in which video signals arecompressed and encoded and an audio elementary stream in which audiosignals are compressed and encoded. Then, these streams are packetizedand multiplexed into a system stream. This system stream is a motionpicture file. In addition, information for rights about video and audiocontents and other auxiliary information may be multiplexed togetherinto the system stream.

Conversion of a file format of pictures stored in the PC 20 into a fileformat that can be displayed on the TV set is performed as follows.First, a system stream of a format of pictures stored in the PC 10 isdemultiplexed into video and audio elementary streams. Then, the videoelementary stream is decoded and then re-encoded into an elementarystream of a code format that is compatible with the TV set. For audio aswell, similarly, decoding and re-encoding are performed. Then, the videoand audio elementary streams resulting from the re-encoding aremultiplexed into a system stream of a format compatible with the TV set.Thus, a converted motion picture file is created. In this way, theserver converts the file format of pictures stored in the PC 10 into amotion picture file of a format that can be displayed on the TV set.

(6) Receiving and Viewing Pictures (Step S107)

The receiver chooses the video delivery service on the screen of FIG.15. Following the screen to accept the sender as in FIG. 11, a receivede-mail list display screen as in FIG. 24 is displayed. Using the remotecontroller, the receiver may move the cursor to any of icons #1 to #9,select a desired e-mail, and press the Fix button. If the selectede-mail is a set of still pictures, a picture list display screen as inFIG. 25 is displayed. When the receiver selects a desired picture bymoving the cursor to any of icons #1 to #9, the selected picture isenlarged and displayed as in FIG. 26. If the picture content selected inFIG. 24 is a motion picture, the motion picture is reproduced fullscreen. Of course, the motion picture may be displayed in a part of thescreen as in FIG. 26.

(7) Downloading and Erasing Pictures

If the TV set 20 has the storage 26 such as HDD, picture contentexisting on the server 30 can be downloaded and stored. When choosing a“Select and download” button in FIG. 24, a screen to select and downloadan e-mail as in FIG. 27 is displayed. When the receiver selects adesired icon and presses the Execute button, a confirmation screen as inFIG. 28 is displayed. When choosing “Yes”, a screen indicating adownload in process is displayed and content is stored into the HDD.Upon normal termination of the download, a screen indicating a downloadcompleted as in FIG. 30 is displayed. Upon abnormal termination of thedownload, the download failure is displayed on the screen.

In the first embodiment, because the receiver is authorized to erasecontent, a “Select and put in the recycle bin” button is displayed inFIG. 24. In the same procedure as for downloading, it is possible toselect an icon and erase the content by pressing this button.

Of course, the sender may be authorized to erase content. The sender mayidentify and erase a motion picture file transferred to and have itpreserved on the server from the PC operation history. In the previoussection (5), picture file format conversion processing in the server 30was described. In conjunction with this conversion processing, when fileerasures should be performed and a file of which type of format shouldbe erased are considered. For a certain picture file, an example whereformat A for PC A is converted into format B for TV set is considered.The server 30 preserves A and, after converting A into B, updates theunread e-mail check table 33 in FIG. 4 and the content management tablein FIG. 8 and enables the receiver to view the content. According totiming when the sender issues a erase command, preferably, processingshould be performed as follows.

(a) If the file remains as A, A is erased and no conversion processingis performed.

(b) During conversion from A into B, the conversion processing isstopped and both A and B being created are erased.

(c) After conversion into B, both A and B are erased, and the unreade-mail check table and the content management table are updated.

As described above, it is possible to authorize the sender and/or thereceiver to erase files.

(8) Temporarily Rejecting the Reception (Step S107)

When choosing “Sender list” in FIG. 24, a sender list screen as in FIG.31 is displayed. If the receiver chooses “I don't decide about it now”without rejecting the acceptance in FIG. 16, after selecting the videodelivery server, when choosing “Sender list” in FIG. 24, the sender listincluding information for the sender waiting to be accepted is displayedas in FIG. 31. This TV set owner, after accepting two persons, Goro andHanako as senders, temporarily rejected the reception from Hanako. Then,the receiver is requested from Taro to accept him as a sender. Whenpressing the Fix button with the cursor positioned in the row of Taro, ascreen to accept a sender as in FIG. 32 is displayed and the receivermay choose “O=acceptance” or “X=rejection”. When pressing the Fix buttonwith the cursor positioned in the row of Goro, a screen to stopreception as in FIG. 33 is displayed and it is possible to change from astate in which “I receive video” to a state in which “I don't receivevideo”. Conversely, when pressing the Fix button with the cursorpositioned in the row of Hanako, a screen for Hanako is displayed and itis possible to change from a state in which “I don't receive video” to astate in which “I receive video” in a similar manner as in FIG. 32.

Although it is not necessary to enter a password on the TV screen in thefirst embodiment, needless to say, it is possible to prompt the receiverto set a password. One way of using the password is such that thereceiver is prompted to enter the password when temporarily rejectingthe reception or accepting the reception of video. It is also possiblethat, when the sender decides to put a parental lock on some video, theparental locked video content transmitted from the sender cannot beviewed unless the receiver enters the password that was set. Of course,such usage is possible that the sender sets a password on an e-mail andtransmits the e-mail and the receiver cannot open it unless entering thepassword. In FIG. 19, an example is presented in which options to set apassword and to set a parental lock are added.

Second Embodiment

In a second embodiment, the sender uploads content to the server 30 byusing a mobile phone 50.

In the content delivery system shown in FIG. 1, the sender, once havingregistered with the server as a member, is able to transmit picturescaptured by the mobile phone 50 to the TV set 20 of a receiver whoaccepted the sender. In this case, uploading pictures is performed usinge-mail software installed in the mobile phone. The reason for this is asfollows. It is practically possible to specify destinations and uploadpicture files to the server 30 without using e-mail software, asdescribed in the previous section (4). However, specifications arelikely to differ among carriers and mobile phone manufacturers and it istherefore supposed that a lot of man hours are required for testing. Inthe second embodiment, therefore, the system adopts a method oftransmitting picture files to the server 30 using e-mail softwareinstalled in the mobile phone, wherever possible, avoiding proprietaryspecifications.

First, the sender registers a mobile phone 50 serving as a transmittingterminal with the server from the PC 10. When choosing “register/editmobile phones” in the left part of FIG. 18 and FIG. 19, a screen toregister/edit mobile phones as in FIG. 21 is displayed. Here, thisexample indicates that the e-mail addresses of nine mobile phonesassociated with one sender ID are registered. This screen allows amaximum of 10 addresses to be registered, taking account of the numberof people in a family and a person who has two or more mobile phones.After entering the e-mail address of a mobile phone in an empty row andthe name of a person who owns the mobile phone, press the Transmitbutton.

Scheme 1, Scheme 2, and Scheme 3 are possible as a method oftransmitting content using a mobile phone.

<Scheme 1> A Method of Assigning e-Mail Addresses to all Receivers.

FIG. 22 is a PC screen to acquire URL to access the server 30 from themobile phone 50. Acquiring URL is possible in the following three ways.

(a) URL is transmitted to the mobile phone 30 by e-mail. When the senderchooses a checkbox of a mobile phone 50 to which the sender wants totransmit URL, the sever 30 transmits the URL enabling login to themobile phone 50.

(b) URL is obtained by causing a mobile phone 50 to read QR codedisplayed on the PC screen.

(c) Manually input URL into a mobile phone 50.

By means of (a) to (c), the mobile phone 30 can obtain URL or URL can beinput to the mobile phone. A web screen to accept access from the mobilephone 50 is prepared on the server 30 and the mobile phone 30 accessesthis URL and logs into the system.

FIG. 23 shows a screen to log in using the mobile phone 50. The senderlogs into the system with the user ID acquired for the video deliveryservice and his or her password. The server 30 displays a list ofreceivers to which this sender can transmit content from the sender DB34. Here, the server displays the names of the receivers registered bythe sender (in the field “name of this destination” in FIG. 12) insteadof displaying device IDs. The server 30 assigns an e-mail address toeach receiver beforehand and stores it in the sender DB 34 and thereceiver DB 35. When the sender selects a destination from among thereceivers displayed on the screen of the mobile phone 50, the mailer isactivated and the selected receiver's e-mail address is inserted in theTO (destination) field. Subsequently, the sender attaches a picturefile(s) and transmits the e-mail according the method of transmitting ane-mail. Because no e-mail software exists in the TV set, the picturefile(s) is actually transferred to the server 30. The server 30determines which device ID to which the e-mail should be transmittedfrom the e-mail address of the receiver and the receiver DB.Subsequently, the server 30 preserves the picture file(s).

<Scheme 2> An Implementation Method with Only One e-Mail Address of theServer 30.

While scheme 1 assigns e-mail addresses to all receivers, scheme 2 usesonly one e-mail address of the server 30. Although the e-mail addressesof receivers are described in FIG. 6 and FIG. 7, they do not exist inscheme 2. When any receiver is selected from among receivers P1 to P9 inFIG. 23, the mailer of the mobile phone is activated, specifying thee-mail address of the server 30 in the destination field. The server 30recognizes the receivers P1 to P9, retrieves the device ID of the otherparty to which the sender wants to transmit content from the receiverDB, and describes the device ID of the receiver in the e-mail text. Uponarrival of the e-mail at the serer 30, the server recognizes the deviceID described in the e-mail text and preserves the picture file(s).

<Scheme 3> A Method of Transmitting Receivers' e-Mail Addresses from theServer to the Mobile Phone.

Although e-mail addresses are assigned to all receivers as is the casefor scheme 1, picture files are transmitted only with e-mail softwareincorporated in the mobile phone 30 and the web screen to accept accessfrom the mobile phone 30 is not prepared on the server 30 in scheme 3.As in FIG. 22, the sender checks a check box of a mobile phone that thesender wants to use to transmit content. A button “transmit to themobile phone destination e-mail addresses to be used for transmissionfrom the mobile phone” (not shown in FIG. 22) is prepared. When thesender presses this button, the server 30 retrieves receivers to whichthe sender can transmit content from the sender DB and the e-mailaddresses of the receivers assigned by the server 30 and the names ofthe receivers are transmitted to the selected mobile phone. From thesee-mail addresses of the receivers, the sender selects an e-mail addresson the mobile phone and activates the mailer.

In scheme 1 and scheme 3, despite that the TV set does not have e-mailsoftware, the sender transmits e-mail in the same procedure astransmitting e-mail, but it actually transmits the e-mail to the server30. Preferably, the sender can easily change the e-mail addressesassigned to the TV sets for security protection. When choosing “Add/Editdestinations” displayed in the left side of the screen in FIG. 21 andFIG. 22, the screen of FIG. 20 is displayed. On this screen, the sendercan change or delete destination IDs and names and change e-mailaddresses (assigned from the server 30). In the case of scheme 2, theaddress of the server 30 displayed when the mailer is activated shouldpreferably be changed periodically and notified to the sender.

The example of transmitting content from a mobile phone 30 usingstandard e-mail software in view of work hours for testing wasdescribed. On the other hand, for uploading from PC, the example wasdescribed in which the web screen to accept access from PC is preparedon the server 30 and picture files are transmitted using this screen.This method is more usable, as it enables reordering picture files andprovides a thumbnail display of a typical scene in each file. Needlessto say, e-mail software installed in the PC 10 may be used to transmitcontent by the PC 10 in a similar manner as for the mobile phone 30.

Third Embodiment

In a third embodiment, a method of charging for the video deliverservice” is described. There are two rate plans, i.e., flat-rate andmetered-rate plans. In flat-rate charging, a service fee is fixed up toa certain capacity and a predetermined capacity of a hard disk isallocated to the user, if the user pays a fixed fee a month. On theother hand, in metered-rate charging, a user is charged a fee each timethe user uses the service. Such a manner of operation is conceivablethat, for example, a fee of 500 yen is set for using the service once upto 5 GB and the server 30 forcibly erases content after two weeks,regardless of whether the receiver may or may not view the content. Theoperator wants to make an efficient use of the system's shard diskcapacity. Hence, if preserved content is delivered early to a receiverand the receiver erases the content, the server 30 can be operatedefficiently, which is beneficial for the operator. Therefore, inmetered-rate charging, the server checks the content management table ofFIG. 8 before displaying the screen of FIG. 24, identifies a picturefile preserved at a metered rate and may display a message such as “Ifyou erase the file until mo O day O, the preservation fee will be halfoff.” beside the file. If a receiver having a TV set with aself-contained hard disk downloads content early and erases it, thisprovides benefit for both the sender and the operator, as charges on thesender is reduced and the operator can utilize the system's hard diskresources efficiently.

Although sender charging is assumed in the third embodiment, receivercharging is also possible. In that case, when a user makes a tentativeregistration, the user may choose one of three types: (1) sendercharging, (2) receiver charging, (3) basically, sender charging, butreceiver is charged in case of extension of a period. In the cases of(2) and (3), prior to a definite registration, such a procedure shouldpreferably be performed that the service provider sends a receiver bymail a form in which a draft on procedure, a credit card number and itsexpiry date, etc. should be written in by the receiver. It is possibleto recommend receiver charging in the following way: when the screen ofFIG. 24 is displayed, “expiry date mo 0 day 0” is displayed beside apicture file with an impending expiry date known from the receiver DB ofFIG. 8; and, after the receiver reproduces the file or when the cursoris positioned at the picture file, a message such as “Would you like tochange to receiver charging? A preservation fee of 00 yen a mount up toO gigabytes.” is displayed. If (2) receiver charging or (3) receivercharging in case of extension of a period is chosen at a tentativeregistration, such charging is effected, as the charging procedure iscompleted. Only if (1) sender charging is chosen, the above procedureshould be performed to recommend change to receiver charging. Thismethod is effective for satisfying a receiver's need to view some morecontent than the capacity of the hard disk incorporated in thereceiver's TV set by paying a fee.

Needless to say, it is possible to change the course (flat-rate,metered-rate), withdraw from membership, etc. by operating the PC 10.

The above-described charging methods are applicable to other embodimentswith another server configuration which will be described later.

Fourth Embodiment

FIG. 34 is an example of an overall architectural diagram showing acontent delivery system according to a fourth embodiment. This system isconfigured such that a transmitting terminal (PC 10), a receivingterminal (TV set 20), a delivery server (delivery server 30) whichrelays a content delivery between both terminals, and an authenticationserver (authentication server 70) are connected to a network 4 such asInternet. In this system, from the PC 10 having e-mail software, picturecontent belonging to the sender is transmitted to a TV set 20 having noe-mail software via the delivery server 30. Hereinafter, the contentdelivery service carried out by the center 3 (delivery server 30) willbe referred to as “video delivery service”.

The sender residing in the sender's home 1 copies picture content(hereinafter, also referred to as a picture file or video) captured by avideo camera 11 or digital camera 12 to the PC 10. The PC 10 connects tothe network 4 via routers (not shown) and transfers the picture to andhas it preserved on the delivery server 30 situated in the center 3. Thedelivery server 30 preserves the picture transferred from the sender (PC10) and waits for access from the TV set 20 in the receiver's home 2 ofa receiver specified by the sender. After the TV set 20 connects to theauthentication server 70 (described herein as the server operating as anentrance to all services, but another dedicated entrance sever mayexist) situated in the center 3 via the routers and the network 4, whenthe receiver chooses “video delivery service”, the TV set 20 receivesthe URL for the service together with a one-time ID from theauthentication server 70, then connects to the delivery server 30 for“video delivery service” and transfers the one-time ID thereto. Thedelivery server 30 transfers the one-time ID received from the TV set 20to the authentication server 70 and receives the receiver's device ID.If this ID matches with the receiver's device ID provided from thesender and preserved on the server, the deliver server 30 transmits amessage indicating arrival of the picture to the TV set 20 and thismessage is displayed on the screen of the TV set 20. After that, thereceiver can select, receive and view the picture. If the TV set 20 hasa self-contained storage (e.g., a hard disk), the picture can also bedownloaded.

In the system of the fourth embodiment, to identify the TV set 20 whichis the receiving terminal, the device ID of each TV set 20 is used as anaddress. Besides picture transmission from the PC 10 in the sender'shome, the sender can transmit a picture file captured by a mobile phone50 which has been registered beforehand with the server from the mobilephone 50 to the deliver server 30 via the network 4, which will bedescribed in a fifth embodiment.

Next, the delivery server 30, the authentication server 70, and the TVset 20 are described in detail regarding their internal structures. Theinternal structure of the delivery server 30 is the same as that of theserver 30 in FIG. 2. The network transceiver 31 is connected to anexternal network 4 and communicates with the authentication server 70,PC 10, and TV set 20 via the network.

The member information manager 32 has data bases and tables, i.e., anunread e-mail check table 33, a sender DB 34, a receiver DB 35, a TVdevice DB 36, and a content management table 37 to store information forsenders and receivers and preserved contents information. When thedeliver server is accessed from a PC 10 or TV set 20, the memberinformation manager 32 performs processing for member informationverification, registration, or others, referring to a related databaseor table.

FIG. 35 is a diagram showing an exemplary internal structure of theauthentication server 70.

A network transceiver 71 is connected to an external network 4 andcommunicates with the delivery server 30, PC 10, and TV set 20 via thenetwork.

A member information manager 72 has a database and table, i.e., a TVdevice DB 76 and a one-time ID management table 77 to store informationfor TV devices and subscription service information. When theauthentication server is accessed from a TV set 20 or a service server(e.g., delivery server 30), the member information manager 72 performsprocessing for device information verification, registration, or others,referring to a related database or table.

When the authentication server is access from the TV set 20 for thefirst time, the member information manager 72 registers the device ID ofthe TV set 20. When the receiver chooses a service, the memberinformation manager 72 links the device ID with the selected service IDand registers both IDs into the TV device DB.

For example, if the deliver server 30 receives data for a tentativemember registration from the PC 10 of a sender, the member informationmanager 32 registers information for device ID, user ID, etc. into theunread e-mail check table 33. If the deliver server receives a responseas to whether the receiver accepts the sender from the TV set 20, themanager 32 updates the contents of the sender DB 34 and the receiver DB35 according to the response. If the delivery server is accessed from aTV set 20, the manager 32 acquires a one-time ID issued from the server70 from the TV set 20, queries the authentication server 70 for one-timeID matching, and acquires the device ID from the TV set 20. In thisprocedure, it can also verified at the same time whether or not theone-time ID is valid. The manager 32 compares the acquired device IDwith information stored in the TV device DB 36 and verifies whether thedevice ID is valid. In case the device ID is invalid, the manager 32detects the invalidity at this point of time and rejects subsequentprocessing for the TV set. The content management table 37 is used tomanage preserved contents transferred from users and hold serviceagreements made with each user.

The content transceiver 38 receives picture content from the PC 10 andtransmits picture content to the TV set 20. The content storage 39stores picture contents received and to be transmitted. Specifically,the content transceiver 38 stores picture content uploaded from the PC10 into the content storage 39 and, in response to a request from the TVset 20 for a picture to receive and view or a request to download apicture, reads the picture content from the content storage 39 andtransmits it to the TV set 20.

FIG. 3 is a diagram showing an exemplary internal structure of the TVset 20. The network transceiver 21 is connected to an external network 4and performs communication with the authentication server 70 anddelivery server 30 via the network. The browser 22 renders screeninformation such as an e-mail screen and an acceptance screen andoutputs it to a display 27 according to information described in a formof HTML, BML, etc. transmitted from the authentication server 70 anddelivery server 30. The picture reproducer 23 decodes a still or motionpicture file contained in picture content transmitted from the deliverserver 30, reproduces the still or motion picture, and outputs it to thedisplay 27.

The device ID sender 24 reads device ID information assigned to the TVset 20 from the device ID storage 25 and sends it to the authenticationserver 70. In the device ID storage 25, the device ID informationspecific to the TV set 20 is stored and retained. This device IDinformation is assigned to each terminal and written into the device IDstorage 25 during the manufacturing of the TV set 20. When the userwants to know the device ID, the user can retrieve it and display on thedisplay 27, e.g., by operating the remote controller.

The content storage 26 is, for example, a hard disk storage device andpicture content received from the delivery server 30 is downloaded andstored into it. The user can read a picture stored and view it via thepicture reproducer 23 at any time the user wants to do. The storage 26may be either self-contained or external. The display 27 displayspictures and/or information output from the browser 22, picturereproducer 23, and device ID sender 24 on the screen.

A process flow of the content delivery service (video delivery service)of the fourth embodiment is described using FIG. 4. The process of thefourth embodiment is nearly the same as the process of the firstembodiment and differences between this embodiment and the firstembodiment are only described. In the flowchart of FIG. 4, the sever 30for the first embodiment should be replaced with the delivery server 30.

Steps S101 to S106 are the same as for the first embodiment.

Step S107: When a receiver accesses the authentication server 70 fromits TV set 20, an one-time ID is issued from the authentication server70. The receiver transmits this ID to the delivery server 30 whenaccessing the delivery server 30. The delivery server 30 transmits theone-time ID received from the TV set 20 to the authentication server 70and receives the device ID verified by device ID matching. The deliveryserver 30 looks through the unread e-mail check table 33 and checks theentry of the device ID. If an unread e-mail flag is set for the deviceID of the accessing TV set 20, it means that the receiver has not yetreceived the e-mail (picture content). In that case, the delivery server30 notifies the TV set 20 that pictures addressed to it arrived at theserver. The receiver selects a desired picture, receives it from thedelivery server 30, and views it on the TV set 20.

Steps S108 and S109 are the same as for the first embodiment.

In addition to the advantages provided by the server configuration ofthe first embodiment, the service provisioning by the serverconfiguration according to the fourth embodiment further provides thefollowing advantages:

(d) By establishing the authentication server as the management serverspecialized for TV devices, high load processing tasks can be assignedto the server for services to be added and it becomes possible to add avariety of services.(e) By management of device IDs on the authentication server,information managed by the authentication server becomes simple andessential. The delivery server can concentrate on management ofinformation relevant to the service and its processing also becomesessential. This facilitates the management of services.(f) By direct access from TV sets to the authentication server (theauthentication server is used as the entrance in the fourth embodiment),not only fraudulent services can be prevented, also secure serviceprovision by double check can be achieved, as all services have to passthe device ID matching in the authentication server.

In the following, each of the steps of the content deliver service inFIG. 4 will be explained in greater detail. The process of the fourthembodiment is nearly the same as the process of the first embodiment anddifferences between this embodiment and the first embodiment are onlydescribed.

(1) Telling the Sender the Receiver's Device ID and Server's URL (StepS101)

Besides the first embodiment, at the authentication server 70 in thisembodiment, the member information manager 72 in FIG. 35, afteracquiring the converted device ID from the TV set, can restore it to thedevice ID being before converted, stored in the device ID storage 25 ofthe TV set by reverse conversion of the device ID converted in the TVset. The member information manager 72 stores the reconstructed deviceID into the database at the first time access from the TV set. Anexample of the device ID DB is shown in FIG. 36. The device ID is usedto manage each device ID and a service ID being used by the device. Forthe one-time ID that is used for device ID matching queried from thedeliver server 30, the authentication server 70 issues, deletes, andmanages it as a unique ID linked with the device ID and service ID. FIG.37 shows the one-time ID management table.

The TV set owner tells the other party (his or her family, friends,relatives, etc.) from whom he or she wants a video transmission theconverted device ID of his or her TV set and the URL of the portal(server) of the service provider by telephone or fax and requests theother party to make a member registration for the “video deliveryservice”.

(2) Tentative Member Registration (Step S102)

The sender executes a member registration (tentative) for the “videodelivery service”, using the converted device ID and the server's URLacquired from the receiver. The PC 10 of the sender is equipped with thebrowser 22 and the following operations are performed by the browser.From the PC 10, the sender accesses the above URL and proceeds with themember registration. The delivery server 60 restores the converteddevice ID entered by the sender to the device ID and then registers thelatter into the DB. FIGS. 9 through 14 show the display screens formember registration. In these display screens, the term “destination ID”which is easy to understand for the user is used instead of converteddevice ID. In the following, “destination ID” has the same meaning as“converted device ID”. Other descriptions about member registration arenot repeated, because they are the same as for the first embodiment.

(3) Acceptance by the Receiver and Definite Member Registration (StepsS103, S104)

When the receiver accepts the sender, the sender executes a definiteregistration from the tentative member registration and the deliverserver 30 adds the definite registration contents to the sender DB 34and the receiver DB 35.

FIG. 6 shows an example of the sender DB. The tentative registrationcontents are inserted in the columns from “user ID” to “birth date” andthe device ID (restored from the converted device ID entered at thetentative registration) of the TV set of the receiver who accepted toreceive (permitted transmission) with the count of receivers=1 isregistered upon the definite registration. Others are the same as forthe first embodiment.

(4) Uploading Picture Files from PC (Step S105)

Uploading is performed in the same way as for the first embodiment.

(5) Picture Format Conversion (Step S106)

Picture format conversion is performed the same way as for the firstembodiment.

(6) Receiving and Viewing Pictures (Step S107)

Using the TV set 20, the receiver connects to the authentication server70 (also serving as the portal site). The TV set encrypts and transmitsdata in which the device ID and authentication data are combined to theauthentication server 70. The authentication data termed herein is,inter alia, information representing the device type such as, e.g., themanufacturer name and model number of the TV set 20. In this embodiment,information representing the device type is referred to as a model ID.The authentication server 70 extracts the authentication data and deviceID from the encrypted data and checks whether those satisfy conditionsfor connection (whether those correspond to a connectable device typeand registered device ID). If rejecting the connection, theauthentication server 70 returns an error t the TV set; if permittingthe connection, it transmits the top page (the screen of FIG. 15) to theTV set 20 and this page is displayed on the TV set 20.

When choosing the video delivery service on this screen, the TV set 20receives from the authentication server 70 the URL of the deliveryserver 30, which is necessary to connect to the service and the one timeID issued by the authentication server 70 (the one-time ID is issued bythe member information manager 72 of the authentication server 70, whenrequested from the TV set 20 or the like, registered in the one-time IDmanagement table 77, and transmitted from the network transceiver 71 tothe requesting device, i.e., the TV set 20 or the like). Using thisinformation, the TV set 20 connects to the delivery server 30 andtransmits the one-time ID.

The delivery server 30 transmits this one-time ID to the authenticationserver 70 and the authentication server 70 checks the entry of theone-time ID in the one-time ID management table 77. Further, theauthentication server 70 checks the TV device DB 76 from the deviceidentifying ID that can be obtained from the one-time ID managementtable 77. It checks whether the device is associated with a service IDcorresponding to the service provided by the delivery server 30. If theservice ID is not registered, the authentication server 70 may return anerror.

If the error is returned from the authentication server 70, the deliveryserver 30 returns to the TV set 20 information indicating that thedevice is unable to connect to the service. If the device ID can beacquired from the authentication server 70 properly, the delivery server30 refers to the entry of the device ID in the TV device DB 36. Itmatching is verified, the delivery server 30 transmits information todisplay the screen to accept the sender 11.

The above-described authentication will be detailed later. Following thescreen to accept the sender as in FIG. 11, the TV set 20 displays thereceived e-mail list display screen as in FIG. 24. Using the remotecontroller, the receiver may move the cursor to any of icons #1 to #9,select a desired e-mail, and press the Fix button. If the selectede-mail is a set of still pictures, a picture list display screen as inFIG. 25 is displayed.

When the receiver selects a desired picture by moving the cursor to anyof icons #1 to #9, the selected picture is enlarged and displayed as inFIG. 26. If the picture content selected in FIG. 24 is a motion picture,the motion picture is reproduced full screen. Of course, the motionpicture may be displayed in a part of the screen as in FIG. 26.

(7) Downloading and Erasing Pictures

Downloading and erasing pictures are performed in the same way as forthe first embodiment.

In the fourth embodiment also, the sender can upload content to thedelivery serve 30 using a mobile phone 50, as is the case for the secondembodiment.

According to the fourth embodiment, the server manages devices by deviceID, but sends the user the converted device ID for service use. Thismerit is avoiding an accident that an erroneous ID input by the sendercauses transmission of content to an unintended user or device.

Here, the authentication process in the fourth embodiment is explainedbelow.

FIG. 38 is a flowchart illustrating an authentication flow for thecontent delivery service of this embodiment.

Step S201: When the receiver accesses the portal site, the receivingterminal (TV set 20) transmits to the authentication server 70authentication data (e.g., the model ID indicating the device type) andthe device ID (ID specific to the device, e.g., a production number)together through a secure channel (e.g. SSL communication channel). Acookie function provided in the browser of the receiving device may beused.

Step S202: In the authentication server 70, the member informationmanager 72 is responsible for various processing tasks. In theauthentication server 70, authentication data is retrieved and it isverified whether the device can make use of the service (cookie may besubjected to a validity check). The TV device DB 76 is referred to checkif the device ID is registered. If the device is judged as invalid orunsupported, the authentication server 70 notifies the receivingterminal of that judgment.

If, for example, authentication data is a model ID indicating the typeof the device, and if the model ID denotes a product made by themanufacturer (service provider), it is judged that the device can makeuse of the service. The model ID of the device that can make use of theservice is stored in a model ID information DB, which is not shown, inthe authentication server 70.

A device ID is associated with a service ID registered in the TV deviceDB 76. It is checked whether the service requested by the accessing useris associated with the device ID of the TV set 20 used by the user.

The receiving terminal presents a result of authentication to the userwith a display or the like. If the receiver's device is authenticatedproperly, the authentication server 70 issues and one-time ID that isused for query from the delivery server 30. Accordingly, in case aterminal makes access falsifying a part of information for the receivingterminal, the authentication server 70 rejects this and abuse can beprevented.

Step 203: The authentication server 70 maintains the one-time ID in theone-time ID management table 77 and transmits to the receiving terminalthe one-time ID together with URL information of the service server(e.g., delivery server 30) selected by the user. If no access has beenmade from the receiver for a certain period of time, the one-time ID maybe deleted.

Step 204: The receiving terminal transmits the one-time ID received fromthe authentication server 70, when making access to the service.

Step 205: In the delivery server 30, the member information manager 32is responsible for various processing tasks. The delivery server 30transmits the one-time ID to the authentication server 70.

Step 206: the authentication server 70 searches the table for a matchwith one-time ID received from the delivery server 30. If the once-timeID registered is not found, the authentication server 70 returns anerror; if it is found, the authentication server 70 returns the deviceID. The one-time ID entry once verified is deleted to invalidate it forsecond time and subsequent access. This enables secure authenticationavoiding false impersonation.

Step 207: The delivery server 30 searches the database for a match withthe device ID received from the authentication server 70. Once havingverified that the device ID belongs to the user joined the service, thedelivery server 30 starts the service provision to the receivingterminal. That is, it begins the delivery of content.

Step 208: The receiving terminal starts to receive and store orreproduce content from the delivery server 30.

Fifth Embodiment

The previously described embodiments, the authentication server 70authenticates a device or user by using the device ID as the ID formanagement. In the fifth embodiment, a unique ID (hereinafter, referredto as device identifying ID) that is generated using the device ID isused to cope with a case where the user replaces the device for usingthe service. This provides the following advantages:

(1) It is prevented that the device recycled by replacement or the likeis used by a third party fraudulently.(2) database expansion is prevented, as the server does not need tomanage unnecessary IDs.As above, it is possible to further improve the operability of thesystem. Then, the following will describe the embodiment where thisdevice identifying ID is used.

In the authentication server 70, the member information manager 72issues a unique device identifying ID that does not match another IDissued as appropriate and registers it into the database (TV device DB76). FIG. 39 shows an example of the TV device DB. FIG. 40 shows anexample of the one-time ID management table. In the TV device DB 76,device identifying ID, device ID, and service ID of a service being usedby the user are managed. In the one-time ID management table, deviceidentifying ID, one-time ID, and service ID are managed.

FIG. 41 is a flowchart illustrating a process flow regarding deviceidentifying ID. The process is described below in order of steps.

Step S301: The user accesses the authentication server 70 (also servingas the portal server herein) to which the receiving terminal (TV set 20)is connected in order to display the initial screen (FIG. 15) to useservices. The TV set 20 transmits authentication data and the device IDto the authentication server 70.

Step S302: The authentication server 70 refers to the contents of the TVdevice DB 76 based on the above information (the authentication data andthe device ID of the TV set 20), verifies whether the ID has beenregistered, and prepares initial screen information suitable for thereceiving terminal.

Step S303: The authentication server 70 transmits this initial screeninformation to the TV set 20 herein via the network transceiver 71. TheTV set 20 receives this by the network transceiver 21 and displays it tothe display 27 via the browser 22.

Step S304: The user may choose the issuance of device identifying ID orthe deletion of device identifying ID directly from the initial screenor through a menu or the like.

Step S305: If the user has chosen the issuance of device identifying ID,the member information manager 72 of the authentication server 70 issuesa unique ID not matching another device identifying ID and registersthis ID into the TV device DB 76 in which the ID is associated with thedevice ID received from the TV set 20. The authentication server 70transmits screen information to notify the issued device identifying IDto the TV set 20 via the network transceiver 71. An example of thescreen that is displayed on the TV set 20 is shown in FIG. 42, where thetop page means the initial screen.

Although not shown, if the user does not yet have a device identifyingID, e.g., when using this service for the first time, a screen shown inFIG. 43 may be displayed to prompt the user to get a device identifyingID, thus providing for further usability. When the user chooses a“Acquire device identifying ID” button in FIG. 43, the authenticationserver 70 issues a device identifying ID as described above. This screenalso allows the user to make sure of the device identifying ID for thepurpose of telling the sender this ID and for other reasons.

Step S306: If the user has chosen the deletion of device identifying ID,the authentication server 70 transmits screen information to confirm thedeletion to the TV set 20 via the network transceiver 71. An example ofthe screen that is displayed on the TV set 20 is shown in FIG. 44, where“Initialize” is equivalent to “delete”. Here, when the user chooses“Initialize”, the member information manager 72 of the authenticationserver 70 deletes the information related to the registered deviceidentifying ID from the TV device DB 76. Although not shown, a screenindicating that the ID was deleted may be displayed on the TV set 20 orthe display may return to the initial screen. In the screen shown inFIG. 44, when the user has chosen “Not initialize”, the display returnsto the initial screen.

Then, the service using the device identifying ID is explained. Theoverall architecture of the content delivery system according to thefifth embodiment is the same as shown in FIG. 34.

In the system of this embodiment, in order to identify a TV set 20 whichis a receiving terminal, the device identifying ID of each TV set 20 isused as an address. For consistency, device identifying IDs are to betransmitted to the authentication server 70 and delivery server 30 andto be told to senders. Thereby, it is easy to cope with user devicereplacement or the like, as already mentioned, and high operability ismaintained. Not only from the PC 10 in the sender's home, the sender canalso transmit a picture file captured by a mobile phone 50, registeredwith the server beforehand, to the delivery server 30 via the network.This is implemented in the previously described manner in the systemdescribed in the fourth embodiment, where device ID is replaced bydevice identifying ID, and repeated description is omitted.

Next, descriptions are provided for the structures of the databases andthe like within the delivery server 30 and the authentication server 70.

FIG. 45 shows an example of the unread e-mail check table 33. In thetable, for each device ID, flags are provided to indicate whether thereis a person waiting to be accepted as a sender and whether a new picturefile has been transferred from an accepted sender. In this example, forthe TV set with the device identifying ID of “1234567”, there are twosenders requesting to be accepted and their user IDs (ID 1, ID 2) arespecified. This example also indicates that an e-mail (actually,pictures) from an accepted user (ID 1) has arrived and the receiver ofthis TV set does not yet read the e-mail.

FIG. 46 shows an example of the sender DB. The tentative registrationcontents are inserted in the columns from “user ID” to “birth date” andthe device identifying ID (already entered at the tentativeregistration) of the TV set of the receiver who accepted to receive(permitted transmission) with the count of receivers=1 is registeredupon the definite registration. Credit card number, expiry date, andjoin data entered by the user at the definite registration areadditionally registered. Since transmission from a mobile phone ispossible, columns for mobile phones are provided and these columns arefilled when a mobile phone is added. The count of receivers=3 in FIG. 46is due to that two receivers are added after the definite registration.

FIG. 47 shows an example of the receiver DB and receiver data isadditionally registered upon the definite registration. Initially, thecount of senders=1 is set and the user ID (user ID 5 in this case) ofthe sender permitted to transmit to the receiver is registered.Subsequently, the user count increments each time another sender ispermitted to transmit to the receiver and its user ID (user ID 6 in thiscase) is added. As information identifying a person in the receiver DB,only the device identifying ID and the name for display are possible toimplement the service. However, taking account of possibility of laterchange to receiver charging, management for such change is facilitatedby entry of address, name, telephone number, and birth date as well. Atthe registration screen of FIG. 12, these items of information may beentered by the user. FIG. 47 shows the contents of the database withthese items of information added. Once sender data and receiver data areadditionally registered in the sender DB and the receiver DB, the sendercan transmit e-mail to the receiver.

FIG. 48 shows a content management table in which device identifying ID,the count of received files for the receiver of the device identifyingID, the names of the files, the User IDs of the senders of the files,rate plans subscribed to by the senders, and their expiry date aremanaged.

Other methods for using the service are the same as described in theabove-described embodiments, excepting that the device ID changes to thedevice identifying ID. So, repeated descriptions are omitted.

As noted from the above, users, the authentication server, and thedelivery server can operate only with device identifying IDs, theusability of users is improved, and the management of the serviceprovider is facilitated.

Sixth Embodiment

The above-described system has the advantage that the management of theauthentication server can be made simpler. However, no consideration istaken for usability in a case where a single user has two or moredevices and for usage in which a single device is used by multiple users(e.g., shared by a family). To cope with this problem, in a system of asixth embodiment, member ID device as well as identifying ID aremanaged. This system is described below.

The overall architectural diagram of the content delivery systemaccording to the six embodiment is the same as shown in FIG. 34, exceptfor an authentication server 80 replacing the authentication server 70.This system is configured such that a transmitting terminal (PC 10), oneor more receiving terminals (TV sets 20), a delivery server (deliveryserver 30) which relays a content delivery between both terminals, andan authentication server (authentication server 80) are connected to anetwork 4 such as Internet. In the previously described “video deliveryservice”, from the PC 10 having e-mail software, picture contentbelonging to the sender is transmitted to a TV set 20 having no e-mailsoftware via the delivery server 30.

Then, the authentication server 80 is described in detail regarding itsinternal structure.

FIG. 49 is a diagram showing an exemplary internal structure of theauthentication server 80.

A network transceiver 81 is connected to an external network 4 andcommunicates with the delivery server 30, PC 10, and TV set 20 via thenetwork.

A member information manager 82 has databases and a table, i.e., amember DB 85, a TV device DB 86 and a one-time ID management table 87 tostore information for members, TV devices and subscription serviceinformation. When the authentication server is accessed from a TV set 20or a service server (e.g., delivery server 30), the member informationmanager 82 performs processing for device information verification,registration, or others, referring to a related database or table.

FIG. 50 is a diagram showing contents that are managed in the member DB85.

A primary member denotes a member that primarily makes use of theservice and this member is assumed to be the owner of the device.Primary member ID, password, and device identifying ID are managed inthe member DB. As a management DB, taking account of extension infuture, name for display, address, name, telephone number, birth date,credit card number and its expiry date in preparation for an integratedcharging service, etc. may be managed in this DB.

FIG. 51 is a diagram showing contents that are managed in the TV deviceDB 86.

In the TV device DB, device identifying ID, device ID, primary memberID, and child member ID are managed.

FIG. 52 is a diagram showing contents that are managed in the one-timeID management table 87.

In this table, device identifying ID, device ID, and one-time ID aremanaged.

The member information manager 82 has a cross-reference function withregard to the above DBs and table.

For example, for an e-mail address that is used for delivery service orthe like, the member information manager 82 generates an address of acombination of an device identifying ID and a member ID, when a memberregistration is executed, and registers this address together with otherinformation into the DB. This enables implementation of a service inwhich, when a user specifies a device identifying ID and a member IDfor, e.g., “video delivery service” or the like, the server transmits avideo to a particular member specified in members sharing a device.

A member registration procedure is described below.

As described in the previously described embodiments, a user registers adevice identifying ID on the TV set 20. As for service ID, when the userchooses a service, the device identifying ID and the service ID of theselected service are linked together and registered into the TV deviceDB. By the operation up to now, the device identifying ID is registeredinto the TV device DB 86.

FIG. 53 is a flowchart illustrating a process flow regarding member IDregistration in the sixth embodiment. The process is described below inorder of steps.

Step S401: A user accesses the authentication server 80 to which thereceiving terminal (TV set 20) is connected in order to display theinitial screen (FIG. 15) to use services. The TV set 20 transmitsauthentication data and the device ID to the authentication server 80.

Step S402: The authentication server 80 refers to the contents of the TVdevice DB 86 based on the above information (the authentication data andthe device ID of the TV set 20), verifies whether the ID has beenregistered, and prepares initial screen information suitable for thereceiving terminal.

Step S403: The authentication server 80 transmits this initial screeninformation to the TV set 20 herein via the network transceiver 81. TheTV set 20 receives this by the network transceiver 21 and displays it tothe display 27 via the browser 22.

Step S404: The user may choose to register member ID or delete member IDdirectly from the initial screen or through a menu or the like.

Step S405: If the user has chosen to register member ID, theauthentication server 80 transmits member ID registration screeninformation to the TV set 20. An example of the screen that is displayedon the TV 20 is shown in FIG. 54, where the top page means the initialscreen.

Step S406: When the user enters necessary information according to thescreen and choose a “Register” button in the screen, the memberinformation manager 82 of the authentication server 80 registers themember ID into the member DB 85 and the TV device DB 86. An example ofthis input screen is shown in FIG. 55. This screen also allows the userto check his or her member ID for the purpose of telling the sender themember ID for other reasons. In the case of first time registration, theauthentication server 80 may present a unique ID to the user. If theuser is a registered member, the user may manually enter and register amember ID.

Although not shown, if the user has entered other personal information,or if a match with registered information has been detected, theauthentication server 80 may transmit a screen including informationlike the table in FIG. 52 to present registered member IDs and presentthe screen to the user. If a primary member registration is not yetdone, the authentication server 80 displays a screen including a maskingor message display indicating that the user cannot register a childmember on the TV set 20 to inhibit the registration.

Step S407: If the user has chosen to delete a member, the memberinformation manager 82 of the authentication server 80 verifies thedevice identifying ID and transmits screen information to confirmdeletion, including a list of deletable members, to the TV set 20 viathe network transceiver 81.

Step S408: An example of the screen that is displayed on the TV set 20is shown in FIG. 56, where the top page means the initial screen. Here,when the user choose a “Delete” button, the member information manager82 of the authentication server 80 deletes information relevant to theregistered member ID from the member DB 85 and the TV device DB 86.Although not shown, a screen for password input may be displayed toreconfirm the deletion before executing the deletion. After thedeletion, a screen indicating that the member ID was deleted may bedisplayed on the TV 20 or the display may return to the initial screen.

As noted from the above, by linking and managing member information anddevice identifying ID on the authentication server 80, detailedmanagement of services on a per-user basis even for users sharing adevice can be accomplished. In a case where a single user has multipledevices, it is possible to make management of services that may beaccessed from multiple devices by a single user.

Although the management using device identifying ID has been discussedin this embodiment, such management can be realized only using deviceID, but not using device identifying ID. If device identifying ID is notused, procedures between the TV set 20 and the authenticationserver/delivery server use device ID.

Then, services that are managed using both member ID and deviceidentifying ID are described below. In case where the sender transmitscontent, specifying a member, a message can be received by entering themember ID and password on the receiving device.

In the system of this embodiment, in order to identify a TV set 20 whichis a receiving terminal, the device identifying ID of each TV set 20 isused as an address. As destination information, by specifyinginformation that is a combination of a device identifying ID and amember ID as an address, it is possible to transmit content to thespecified device and the specified member. For consistency, deviceidentifying IDs are to be transmitted to the authentication server 80and delivery server 30 and to be told to senders. Thereby, it is easy tocope with user device replacement or the like, as already mentioned, andhigh operability is maintained. Not only from the PC 10 in the sender'shome, the sender can also transmit a picture file captured by a mobilephone 50, registered with the server beforehand, to the delivery server30 via the network. This is implemented in the previously describedmanner in the system described in the fifth embodiment, where device IDis replaced by device identifying ID, and repeated description isomitted.

Next, operation by sender for “video delivery service” is descriedbelow.

Although a basic flow is as previously described, particularly when thesender wants to transmit to a member, the sender have to enter not onlya device identifying ID, also a member ID (operation without entering amember ID is the same as described previously).

In the process for content delivery service in FIG. 4, when making atentative member registration (step S102), a screen that is shown inFIG. 57 is provided, which is the screen to enter a device identifyingID of a TV set and a member ID as destination information for servicesthat are managed using member ID in the sixth embodiment. In thisdisplay screen, a term “destination ID” which is easy to understand forthe user is used instead of device identifying ID. The term “destinationID” has the same meaning as “device identifying ID”. When a member IDhas been entered, subsequently, the destination ID and member ID columnsare displayed in other screens. Because the operating procedure and thelike are the same as described previously, repeated description isomitted.

Device ID, content (file name), and member ID are associated with eachother and managed in the content management table. As destinationinformation, by specifying information that is a combination of a deviceidentifying ID and a member ID as an address, the content sender cantransmit content to the specified member having a given member ID. Suchinformation is managed in the content management table.

The delivery server 30 receives a member ID and password transmittedfrom the TV set 20 and transmits content associate with the member IDand device ID to the TV set 20.

A receiver can send a member ID to the delivery server 30 whenrequesting a delivery of content. Alternatively, a receiver may send hisor her member ID to the authentication server 80 when accessing it forthe first time, and the authentication server 80 may issue a one-time IDfor each member ID. If it issues a one-time ID for each member IDinstead of each device ID, a TV set 20 may send only the one-time IDwhen requesting the delivery server for a delivery.

Seventh Embodiment

Further, descriptions are provided for a delivery service for contentcomprising text information (which is hereinafter referred to as amessage) (hereinafter, the service is referred to as a message deliveryservice in this embodiment) by a portal server, wherein the service ismanaged using member ID and device identifying ID. The overallarchitectural diagram for this embodiment is the same as shown in FIG.34, except for an authentication server 80 replacing the authenticationserver 70. This system is configured such that a transmitting terminal(PC 10), a receiving terminal (TV set 20), and a center 3 (a portalserver comprising an authentication server 80) which relays a contentdelivery between both terminals are connected to a network 4 such asInternet. In this system, from the PC 10 having e-mail software and webbrowser software, a message is transmitted to the TV set 20 via thecenter 3. Hereinafter, the message delivery service carried out by thecenter 3 will be referred to as “memo messaging service”.

The following description assumes that the above-mentioned deviceidentifying ID of each device and the member ID of each member areregistered in the previously described embodiment.

By operating the PC 10 connected to the network 4 via routers (notshown), the sender residing in the sender's home 1 accesses a pageprepared by e-mail software or the authentication server 80 andtransmits a message to the authentication server 80. The authenticationserver 80 preserves the message transferred from the sender (PC 10) andwaits for access from the TV set 20 in the receiver's home 2 of areceiver specified by the sender.

After the TV set 20 connects to the authentication server 80 (describedherein as the server operating as an entrance to all services, butanother dedicated entrance sever may exist) situated in the center 3 viathe routers and the network 4, when the receiver chooses “memo messagingservice”, the authentication server 80 transmits a message indicatingarrival of a “memo message” to the TV set 20 and this message isdisplayed on the screen of the TV set 20.

After that, the receiver can select, receive, and read the “memomessage”. If the TV set 20 has a self-contained storage (e.g., a harddisk), the message can also be downloaded. Particularly, when the sendertransits a message, specifying a member, the message can be received byentering a password corresponding to the member ID on the receivingdevice.

In the system of this embodiment, in order to identify a TV set 20 whichis a receiving terminal, the device identifying ID of each TV set 20 isused as an address. As destination information, by specifyinginformation that is a combination of a device identifying ID and amember ID as an address, it is possible to transmit a message to thespecified device and the specified member. For consistency, deviceidentifying IDs are to be transmitted to the authentication server 80and to be told to senders.

Thereby, if the device identifying ID of a device used by the receiveris registered in the authentication server 80, the authentication server80 refers to the database, retrieves the device identifying ID belongingto the receiver, even if the receiver is not registered, directly linkedwith the device identifying ID, and transmits the message which, inturn, can be received by the receiver. It is possible to provide themessage delivery service with high usability.

Not only from the PC 10 in the sender's home, the sender can alsotransmit a message to the authentication server 80 even from a mobilephone 50 via the network 4.

This service may be implemented by providing a dedicated service server,as in the previously described embodiments. In that case, the operationprocedure and the flow for communication with the server are the same asfor “video delivery service”. Communication among restrictive usersbecomes possible and a service that is more secure and handles a widerspectrum of data can be provided. Herein, the following descriptionassumes that simple text information is used as a memo message and thedatabase managed on the authentication is configured to have additionalfunctions of managing messages and senders.

As the simplest configuration, a possible method is that theauthentication server 80 as a portal server transmits operating screensto the device used by the sender by making use of a function (e.g., HTTPserver function) that is used to transmit initial and other screens.Because a normal receiver entrance also serves for deviceauthentication, a dedicated entrance for PCs 10 and mobile phones 50 isprovided.

FIG. 58 is a flowchart illustrating a process flow to transmit a messageby “memo messaging service” in the seventh embodiment. The process isdescribed below in order of steps.

Step S501: The sender accesses a “memo messaging service” transmissionpage on the authentication server 80, using the PC 10.

Step S502: The authentication server 80 transmits “memo message” inputpage information to the terminal PC 10 of the sender.

Step S503: The PC 10 displays the “memo messaging service” transmissionpage received from the authentication server 80 and the sender inputs amessage and a destination (device identifying ID and member ID) to thispage. A screen that is shown in FIG. 59 is the message input screen toenter a device identifying ID of a TV set and a member ID as destinationinformation for services that are managed using member ID in the seventhembodiment.

In this display screen, a term “destination ID” which is easy tounderstand for the user is used instead of device identifying ID. Theterm “destination ID” has the same meaning as “device identifying ID”.After input, the sender chooses a “transmit” button, then the PC 10transmits the message to the authentication server 80. Here, aconfirmation screen as shown in FIG. 60 may be displayed, so that themessage will be transmitted after the sender confirms the messagetransmission.

Step S504: The authentication server 80 registers the message receivedfrom the sender's terminal (PC 10).

FIG. 49 is a diagram showing an exemplary internal structure of theauthentication server 80. However, the TV device DB 86 in this figure isreplaced by a TV device DB 96 in this embodiment.

The network transceiver 31 is connected to an external network 4 andcommunicates with a PC 10 and a TV set 20 via the network.

The member information manager 92 has data bases and a table, i.e., amember DB 85, a TV device DB 96, and a one-time ID management table 87to store information for members and TV devices and subscription serviceinformation. When the server is accessed from a PC 10 or TV set 20, themember information manager 92 performs processing for device informationverification, registration, or others, referring to a related databaseor table.

FIG. 61 is a diagram showing contents that are managed in the TV deviceDB 96.

In this DB, device identifying ID, device ID, primary member ID, childmember ID, and messages registered by “memo messaging service” and theirsender information (e.g., e-mail address) are managed.

Now, the authentication server 80 completes registering a message from asender using the “memo messaging service”.

FIG. 62 is a flowchart illustrating a process flow to receive a messageby “memo messaging service” in the seventh embodiment. The process isdescribed below in order of steps.

Step S601: Using a receiving terminal, a user accesses theauthentication server 80 to which the receiving terminal (TV 20) isconnected. The TV 20 transmits authentication data and the device ID tothe authentication server 80.

Step S602: The authentication server 80 refers to the contents of the TVdevice DB 96 based on the above information (the authentication data andthe device ID of the TV set 20), verifies whether the ID has beenregistered, and prepares initial screen information suitable for thereceiving terminal.

Step S603: The authentication server 80 searches the TV device DB 96 forthe device ID received in the above step and retrieves a primary memberID associated with the device ID. Based on the primary member ID, theserver searches the member DB 85 and retrieves all device identifyingIDs associated with the member ID. The server searches the TV device DB96 again and retrieves information for messages and senders relevant toall retrieved device identifying IDs.

Here, there is no relevant message, the process goes to step S604. Ifthere is the relevant message(s), the process goes to step S605.

Step S604: The server transits normal initial screen (FIG. 15)information to the TV set 20 herein via the network transceiver 31. TheTV set 20 receives this by the network transceiver 21 and displays it tothe display 27 via the browser 22.

Step S604: If there are multiple relevant messages, the server transmits“memo messaging” message list screen information which is shown in FIG.63 to the TV set 20 via the network transceiver 31. The TV set 20receives this by the network transceiver 21 and displays it to thedisplay 27 via the browser 22. When the receiver selects a desiredmessage, a “memo messaging” message display screen shown in FIG. 64 isdisplayed.

If there is one relevant message, the “memo messaging” message displayscreen in FIG. 64 may be displayed, skipping the list screen in FIG. 63.

If the message(s) is intended for a given member, only if the user hasentered a correct password corresponding to his or her member ID via apassword input screen in FIG. 65, the “memo messaging” message displayscreen in FIG. 64 may be displayed.

Even if there is one or more relevant messages, a message list or amessage display screen may be displayed via the normal initial screen(FIG. 15).

As noted from the above, the following advantageous effects areobtained.

For example, in a case where a user who is a receiver (of course, oneperson may be a sender and a receiver) has multiple TV sets 20 in his orher home, assume that a TV set 20 placed in a living room is A and a TVset 20 placed in a den is B. Even if a sender has transmitted a “memomessaging” message, specifying the device identifying ID of the TV set Bas a destination, the user can receive this message, when accessing theportal server from the TV set A place in the living room.

If the authentication server 80 is provided with a dedicated entrancefor TV sets capable of using the “memo messaging service” in thisembodiment, for example, the following function can be realized: whilethe user is viewing the TV, the TV set receives a message by accessingthe dedicated entrance by background operation and superimposes it onthe TV screen.

Further, an example of application of the “memo messaging service”managed using both member ID and device identifying ID to the “videodelivery service” is presented below.

The overall architectural diagram of the content delivery system is thesame as shown in FIG. 34, except for an authentication server 80replacing the authentication server 70. This system is configured suchthat a transmitting terminal (PC 10), another transmitting terminal(mobile phone 50), a receiving terminal (TV set 20), a delivery server(delivery server 30) which relays a content delivery between bothterminals, and an authentication server (authentication server 80) areconnected to a network 4 such as Internet. In the previously described“video delivery service”, from a PC 10 or mobile phone 50 having e-mailsoftware, picture content belonging to the sender is transmitted to a TVset 20 having no e-mail software via the delivery server 30.

In step S105 of the process flow of the content delivery service (videodelivery service) shown in FIG. 4, by carrying out the followingprocessing, the above application can be realized.

By operating the PC 10, the sender specifies a receiver who accepted totransmit to and transmits (uploads) pictures captured by the videocamera or the digital camera to the delivery server 30. The deliveryserver 30 stores the pictures transferred from the PC 10 into thecontent storage 39. Then, the server preserves them until arrival of arequest to receive from the specified receiver. At the same time, thesender transmits to the authentication server 80 a “memo messaging”message that the sender has content addressed to the device identifyingID of the receiver preserved on the delivery server.

Accordingly, when the user accesses the portal server from the receivingterminal and uses “memo messaging service”, the user can know that thereis content addressed to the user's terminal, received by “video deliveryservice”.

Further, in step S603 of the process flow to receive a message by “memomessaging service” in the seventh embodiment shown in FIG. 62, bycarrying out the following processing, a message can be transmitted toonly a receiver who uses the delivery service.

The authentication server 80 searches the TV device DB 96 for the deviceID received in the previous step and retrieves a primary member IDassociated with the device ID. Based on the primary member ID, theserver searches the member DB 85 and retrieves all device identifyingIDs associated with the member ID. The server searches the TV device DB96 again, extracts those associated with a delivery service ID from allretrieved device identifying IDs, and retrieves information for messagesand senders relevant to those.

Accordingly, when the user accesses the portal server from the receivingterminal and uses “memo messaging service”, the user can know that thereis content addressed to the user's terminal, received by “video deliveryservice”, only if, in a set of member IDs associated with the receivingterminal user, there is at least one member ID who uses “video deliveryservice”.

A content delivery system comprising a transmitting terminal, areceiving terminal, and a delivery server which are connected via anetwork and configured to transmit content from the transmittingterminal to the receiving terminal via the delivery server, the deliveryserver comprising a database for registering device IDs, eachidentifying each receiving terminal, a content storage for temporarilystoring contents transmitted from transmitting terminals, and a tablefor sorting and managing contents by receiver terminal's device ID andby sender. In response to a request from a receiving terminal, thedelivery server refers to the table and transmits content destined tothe receiving terminal's device ID to the receiving terminal.

According to the first to seventh embodiments described previously, acontent delivery method for transmitting content transmitted from atransmitting terminal to a receiving terminal via a delivery server isprovided. The method comprises registering a device ID identifying areceiving terminal with the delivery server; sorting and managingcontents by the delivery server, wherein the contents transmitted fromtransmitting terminals are sorted by receiver terminal's device ID towhich each content is destined; in response to a request from areceiving terminal, transmitting by the delivery server a contentdestined to the receiving terminal's device ID to the receivingterminal.

A delivery server storing content transmitted from a transmittingterminal and transmitting the content to a receiving terminal,comprising: a database for registering a device ID identifying areceiving terminal, a content storage for temporarily storing contentstransmitted from transmitting terminals, and a table for sorting andmanaging contents by receiver terminal's device ID and by sender. Inresponse to a request from a receiving terminal, the delivery serverrefers to the table and transmits content destined to the receivingterminal's device ID to the receiving terminal.

A receiving terminal that receives content transmitted from atransmitting terminal via a delivery server is also provided. Thereceiving terminal comprises a device ID storage for storing a device IDidentifying the receiving terminal; a selector for selecting a contentto receive or a content sender; and a display for displaying receivedcontent. By sending the device ID of the receiving terminal to thedelivery server, the receiving terminal acquires and displays a list ofcontents destined to the receiving terminal, stored on the deliveryserver, or a list of senders.

A content delivery system comprising a transmitting terminal, areceiving terminal, a delivery server, and an authentication serverwhich are connected via a network and configured to transmit contentfrom the transmitting terminal to the receiving terminal via thedelivery server, the delivery server comprising a database forregistering device IDs, each identifying each receiving terminal, acontent storage for temporarily storing contents transmitted fromtransmitting terminals, and a table for sorting and managing contents byreceiver terminal's device ID and by sender. The authentication serverstores user information such as the device ID of a device owned by auser and service IDs, temporarily issues and stores a one-time ID, andcomprises a table for associating the one-time ID with the userinformation. In response to a request from a receiving terminal, thedelivery server refers to the table and, after obtaining authenticationas to whether the receiving terminal's device ID is a valid ID by theauthentication server, transmits content destined to the receivingterminal's device ID to the receiving terminal.

In order to transmit content transmitted from a transmitting terminal toa receiving terminal via the delivery server, a device ID identifying areceiving terminal is registered with the delivery server. The deliveryserver sorts and manages contents transmitted from transmittingterminals by receiver terminal's device ID to which each content isdestined. In response to a request from a receiving terminal, thedelivery server, after receiving from the receiving terminal a one-timeID issued by the authentication server and obtaining authentication bythe authentication server using the one-time ID, transmits contentdestined to the receiving terminal's device ID to the receivingterminal.

An authentication method in which a delivery server for storing contenttransmitted from a transmitting terminal and transmitting the content toa receiving terminal, the delivery server comprising a database forregistering device IDs, each identifying each receiving terminal, acontent storage for temporarily storing contents transmitted fromtransmitting terminals, and a table for sorting and managing contents byreceiver terminal's device ID and by sender, the delivery server, inresponse to a request from a receiving terminal, after obtainingauthentication by the authentication server using an one-time ID issuedby the authentication server, refers to the device ID table for a deviceID received and transmits content destined to the receiving terminal'sdevice ID to the receiving terminal.

An authentication server comprising a table for verifying a serviceassociated with user information from information comprisingauthentication data and a device ID received from a device. Theauthentication server issues a one-time ID which is used by a deliveryserver for authentication, temporarily stores a one-time ID associatedwith a receiving device, and authenticates the one-time ID when thereceiving terminal is receiving content transmitted from a transmittingterminal via the delivery server.

A receiving device comprising a device ID storage for storing a deviceID which is used by a delivery server to identify the receivingterminal; a selector for selecting a content to receive or a contentsender; and a display for displaying received content.

The receiving device, by sending the receiving terminal's authenticationdata and device ID to the authentication server, receives a one-time IDand, then, transmits the one-time ID to the delivery server. Thedelivery server transmits the one-time ID to the authentication serverand receives the receiving device ID. The receiving device acquires anddisplays a list of contents destined to the receiving terminal, storedon the delivery server, or a list of senders.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an overall architectural diagram showing an exemplaryembodiment of a content delivery system.

FIG. 2 is a diagram showing an exemplary internal structure of a server30.

FIG. 3 is a diagram showing an exemplary internal structure of a TV set20.

FIG. 4 is a flowchart illustrating a process flow of a content deliveryservice.

FIG. 5 shows an example of an unread e-mail check table.

FIG. 6 shows an example of a sender DB.

FIG. 7 shows an example of a receiver DB.

FIG. 8 shows an example of a content management table.

FIG. 9 shows an example of a login/user registration screen at a sendingside.

FIG. 10 shows an example of a user registration screen (to very theterms).

FIG. 11 shows an example of a user registration screen (to specify adestination).

FIG. 12 shows an example of a user registration screen (to enter memberinformation).

FIG. 13 shows an example of a user registration screen (to confirm theentry).

FIG. 14 shows an example of a user registration screen (tentativeregistration completed).

FIG. 15 shows an example of an initial screen for connecting to theserver at a receiving end.

FIG. 16 shows an example of a screen to accept a sender.

FIG. 17 shows an example of a screen for a definite user registration.

FIG. 18 shows an example of a screen to create an e-mail.

FIG. 19 shows an example of a created e-mail.

FIG. 20 shows an example of a screen to add/edit destinations.

FIG. 21 shows an example of a screen to register/edit mobile phones.

FIG. 22 shows an example of a screen to access from a mobile phone.

FIG. 23 shows an example of a screen to transmit an e-mail from a mobilephone.

FIG. 24 shows an example of a received e-mail list display screen.

FIG. 25 shows an example of a still picture list display screen.

FIG. 26 shows an example of a screen reproducing a motion and/or stillpicture.

FIG. 27 shows an example of a screen to select and download an e-mail.

FIG. 28 shows an example of a screen to confirm the execution ofdownloading.

FIG. 29 shows an example of a screen indicating a download in process.

FIG. 30 shows an example of a screen indicating a download completed.

FIG. 31 shows an example of a sender list display screen.

FIG. 32 shows an example of a screen to accept a sender.

FIG. 33 shows an example of a screen to accept/reject reception.

FIG. 34 is an overall architectural diagram showing an exemplaryembodiment of a content delivery system.

FIG. 35 is a diagram showing an exemplary internal structure of anauthentication server 70.

FIG. 36 shows an example of TV device DB.

FIG. 37 shows an example of a one-time ID management table.

FIG. 38 is a flowchart illustrating a process flow of authentication.

FIG. 39 shows an example of a TV device DB for management using deviceidentifying ID.

FIG. 40 shows an example of a one-time ID management table formanagement using device identifying ID.

FIG. 41 is a flowchart illustrating a process flow regarding deviceidentifying ID.

FIG. 42 shows an example of a screen to acquire and confirm a deviceidentifying ID.

FIG. 43 shows an example of a screen to acquire and confirm a deviceidentifying ID, when the user has no device identifying ID.

FIG. 44 shows an example of a screen to delete the device identifyingID.

FIG. 45 shows an example of an unread e-mail check table for managementusing device identifying ID.

FIG. 46 shows an example of a sender DB for management using deviceidentifying ID.

FIG. 47 shows an example of a receiver DB for management using deviceidentifying ID.

FIG. 48 shows an example of a content management table for managementusing device identifying ID.

FIG. 49 is a diagram showing an exemplary internal structure of anauthentication server 80.

FIG. 50 shows an example of a member DB.

FIG. 51 shows an example of a TV device DB for management using memberID.

FIG. 52 shows an example of a one-time ID management table formanagement using member ID.

FIG. 53 is a flowchart illustrating a process flow regarding member ID.

FIG. 54 shows an example of a screen to register and confirm a memberID.

FIG. 55 shows an example of a screen to newly register a member ID.

FIG. 56 shows an example of a screen to delete a member ID.

FIG. 57 shows an example of a user registration screen (to specify adestination for management using member ID).

FIG. 58 is a flowchart illustrating a process flow to transmit a messageby “memo messaging service”.

FIG. 59 shows an example of a message input screen to enter a deviceidentifying ID and a member ID.

FIG. 60 shows an example of a screen to confirm message transmission.

FIG. 61 shows an example of a TV device DB for management using memberID.

FIG. 62 is a flowchart illustrating a process flow to receive a messageby “memo messaging service”.

FIG. 63 shows an example of a “memo messaging” message list screen.

FIG. 64 shows an example of a “memo messaging” message display screen.

FIG. 65 shows an example of a screen to enter a password of a “memomessaging” member.

LIST OF REFERENCE NUMERALS

-   4 . . . Network-   10 . . . Transmitting terminal (PC)-   20 . . . Receiving terminal (TV set)-   21 . . . Network transceiver-   22 . . . Browser-   23 . . . Picture reproducer-   27 . . . Display-   24 . . . Device ID sender-   25 . . . Device ID storage-   26 . . . Content storage-   30 . . . Delivery server-   31 . . . Network transceiver-   32 . . . Member information manager-   33 . . . Unread e-mail check table-   34 . . . Sender DB-   35 . . . Receiver DB-   36 . . . TV device DB-   37 . . . Content management table-   38 . . . Content transceiver-   39 . . . Content storage-   50 . . . Mobile phone-   70 . . . Authentication server-   72 . . . Member information manager-   76 . . . TV device DB-   77 . . . One-time ID management table-   80 . . . Authentication server-   82 . . . Member information manager-   85 . . . Member DB-   86 . . . TV device DB-   87 . . . One-time ID management table

1. A content delivery system comprising a transmitting terminal, aplurality of receiving terminals, and a delivery server, wherein thedelivery server comprises a database which registers a user ID of asender who transmits a picture content and a user ID of each of aplurality of receivers who receives the picture content in associationwith each other, and a content storage which stores the picture contenttransmitted from the sender, wherein, in a case that the transmittingterminal transmits a new picture content to the delivery server, each ofthe plurality of receiving terminals receives a first notice indicatingthat the new picture content is stored in the content storage, andwherein each of the receiving terminals displays a list of the picturecontents which are transmitted from the transmitting terminal and storedin the content storage, information about a sender who transmitted thelisted picture contents, and a comment inputted by the transmittedterminal.
 2. The content delivery system according to claim 1, whereineach of the plurality of receiving terminals further displays a group ofthe picture contents.
 3. The content delivery system according to claim1, wherein, in a case that each of the plurality of receiving terminalsreceives a second notice which indicates whether or not the deliveryserver registers the user ID of each of the plurality of receivers, eachof the plurality of receiving terminals accepts an access to thedelivery server via the second notice and the delivery server allowseach of the plurality of receiving terminals to download the picturecontent transmitted from the transmitting terminal, and in response to adownloading request from the registered user of each of the plurality ofreceivers, the delivery server transmits the picture content to each ofthe plurality of receiving terminals.
 4. A content delivery systemcomprising a transmitting terminal and a plurality of receivingterminals, wherein the transmitting terminal and the plurality ofreceiving terminals are coupled to a delivery server which comprises adatabase which registers a user ID of a sender who transmits a picturecontent and a user ID of each of a plurality of receivers who receivesthe picture content in association with each other, and a contentstorage which stores the picture content transmitted from the sender,wherein, in a case that the transmitting terminal transmits a newpicture content to the delivery server, each of the plurality ofreceiving terminals receives a first notice indicating that the newpicture content is stored in the content storage, and wherein each ofthe plurality of receiving terminals displays a list of the picturecontents which are transmitted from the transmitting terminal and storedin the content storage, information about a sender who transmitted thelisted picture contents, and a comment inputted by the transmittingterminal.
 5. The content delivery system according to claim 4, whereineach of the plurality of receiving terminals further displays a group ofthe picture contents.
 6. The content delivery system according to claim4, wherein, in a case that each of the plurality of receiving terminalsreceives a second notice which indicates whether or not the deliveryserver registers the user ID of each of the plurality of receivers, eachof the plurality of receiving terminals accepts an access to thedelivery server via the second notice and the delivery server allowseach of the plurality of receiving terminals to download the picturecontent transmitted from the transmitting terminal, and in response to adownloading request from the registered user of each of the plurality ofreceivers, the delivery server transmits the picture content to each ofthe plurality of receiving terminals.
 7. A method for delivering picturecontents among a transmitting terminal, a plurality of receivingterminals and a delivery server which comprises a database whichregisters a user ID of a sender who transmits a picture content and auser ID of each of a plurality of receivers who receives the picturecontent in association with each other, and a content storage whichstores the picture content transmitted from the sender, the methodcomprising the steps of: transmitting a first notice indicating that anew picture content is stored in the content storage from thetransmitting terminal to each of the plurality of receiving terminals ina case that the transmitting terminal transmits the new picture contentto the delivery server; and displaying, by each of the plurality ofreceiving terminals, a list of the picture contents which aretransmitted from the transmitting terminal and stored in the contentstorage, information about a sender who transmitted the listed picturecontents, and a comment inputted by the transmitting terminal.
 8. Themethod for delivering picture contents according to claim 7, furthercomprising the step of: displaying, by each of the plurality ofreceiving terminals, a group of the picture contents.
 9. The method fordelivering picture contents according to claim 7, further comprising thesteps of: in a case that each of the plurality of receiving terminalsreceives a second notice which indicates whether or not the deliveryserver registers the user ID of each of the plurality of receivers andeach of the plurality of receiving terminals accepts an access to thedelivery server via the second notice, allowing, by the delivery server,each of the plurality of receiving terminals to download the picturecontent transmitted from the transmitting terminal, and in response to adownloading request from the registered user of each of the plurality ofreceivers, transmitting the picture content from the delivery server toeach of the plurality of receiving terminals.